Copyright: TFTP Client95


TFTP Client95

for Microsoft® Windows 95®

Copyright © 1995-96, Weird Solutions. All rights reserved.

TFTP Client95 is a Trivial File Transfer Protocol client for Microsoft Windows 95 and Windows NT. The program complies with RFC 1350, “The TFTP Protocol”, as well as the newer “option extension” RFCs 1782,1783 and 1784.

Getting Started:	Further reading:

Contents of this package	Notes on TFTP Client95 operation

Installation

Operation

Troubleshooting


Contents of this package

The TFTP Client95 package should contain four files:

TFTPC.EXE	The TFTP Client95 program

SETUP.EXE	The installation program

TFTPC.HLP	The help file

LICENSE.WRI	License agreement

README.TXT	General notes

If you are missing any of the listed files, download a new version of TFTP Client95.


Installing the program
Installation

Run the SETUP.EXE program to install TFTP Client95. After choosing a directory the setup program will copy all necessary files to the installation directory and create a Start Menu group.

If the setup program detects existing TFTP Client95 files you will be prompted as to whether or not they should be overwritten. Refer to the troubleshooting section if you encounter errors during installation.


Operation

After launching TFTP Client95 you will see a window similar to the one shown below. Click on different areas of the image to find out more about each part of the window. Refer to the section on troubleshooting if you encounter problems when trying to transfer a file.

TFTP Client95 main window


TFTP Client95 Notes

TFTP Client95 can read or write a file in either binary or ASCII mode (referred to as octet and netascii modes in the RFC). Files that are transferred in binary mode are transferred byte by byte, resulting in a mirror image of the original file. This is the default mode, and it should be used for transferring any file that is not in a readable text format.


The author

The author of TFTP Client95, Bud Millwood, may be reached via internet e-mail at the following address:

bud@dataphone.se

Your comments and suggestions are welcomed.


TFTP vs. FTP

The Trivial File Transfer Protocol (TFTP) is not the same as the File Transfer Protocol (FTP); the two are incompatible. It is not possible to use TFTP Client95 to transfer files to or from an FTP server.


This button is labeled either “Get” or “Put” depending on the transfer mode you’ve chosen. Clicking this button actually starts your TFTP transfer.


Close will exit TFTP Client95. Any outstanding file transfer is aborted.


Click the Help button to display this help file.


The About button shows version and copyright information.


This box specifies the name of the source file. For a “Get” operation the source file is the name of the file on the remote server, but for a “Put” operation the source file is the name of a local file to send.


This box specifies the name of the destination file. For a “Get” operation this is the name of a local file (UNC pathnames are fine). For a “Put” operation the destination file is the name of the file to be created on the remote server.


”Remote host” is the name or IP address of the machine you’re going to transfer a file to or from.


The “Block size” box is a TFTP option extension that requests a block size larger (or smaller) than the standard 512 bytes. If the TFTP server you’re transferring from supports this option, the file may require less time to transfer. Any value may be used, but the optimum size is the Path MTU minus the IP and UDP header sizes.


The timeout option is used to ask for a specific timeout during the transfer. You may want to change this value on heavily congested networks.


By default, TFTP Client95 will not overwrite an existing file. Placing a check mark in this box will override this.


This bar shows the progress of the file as it is transferred. Note that the bar will be empty if you are reading a file from a TFTP server that doesn’t support the new “tsize” option.


The details of the transfer are shown here.


This area shows the status of the transfer.


Copyright © 1996, Weird Solutions Sweden


Choose “Get” to dowload a file or “Put” to upload a file.


The mode can be binary (octet) or ASCII (netascii).


Weird Solutions Sweden

Ågatan 4B 2tr

795 31 RÄTTVIK

Sweden

tel: +46 70 566 7803

email: bud@dataphone.se


Octet mode transfers files byte by byte, resulting in an exact duplicate of the file. Octet mode is also referred to as binary mode.


Netascii mode assumes that the file being transferred should be a readable text file. Since different computer systems sometimes store text files in different formats, netascii mode dictates a "generic" mode for a text file during transit. For this type of transfer, the sender translates the text file from its own format to netascii format, then sends the file across the network. The receiver then translates the netascii file to its text file format before storing the file. Because of the translation, a file transferred in netascii may be larger or smaller on the receiving system than it is on the sending system.


Request For Comments. Many RFCs specify Internet standards, although the ones that do so are now being labeled STDs in order to distinguish them from the lovely poems.


Troubleshooting

Problems with installation:

•	Setup won't start

TFTP Client95 requires Windows 95 or Windows NT to run.

•	Setup reports " Error copying file xxx"

If Setup can't find a file, it will report an error but continue to try to install TFTP Client95. Check to see that all of the required files are in the source directory and that the destination drive has enough free space. If you're installing TFTP Client95 over a network, ensure that you have write permission on the destination directory.

•	Setup didn't create Start Menu icons

If setup fails to create the Start Menu icons, you can create them yourself by choosing the Settings->Taskbar option of the Start Menu.

Problems with operation:

•	TFTP Client95 installed fine, but how do I start it?

Click Start on the Start Menu, then find the group Weird Solutions. Click TFTP Client95 to run the program.

•	TFTP Client95 reports “No response from server”

1.	Make sure you're not trying to transfer to or from an FTP Server. TFTP and FTP are not compatible protocols.

2.	Ensure that the TFTP server is functioning and running a TFTP server service.

3.	Ensure that IP works on the client and server systems. Try to ping the server.

4.	If you're using a host name, bypass your name resolver by specifying the TFTP server’s IP address.

5.	If the server is multi-homed, try specifying another interface.

6.	Try using the server system as both client and server, and specify the loopback address as the tftp server address. (You'll need a Windows tftp server for this)

7.	If all else fails, e-mail bud@dataphone.se and describe your setup.

•	TFTP Client95 reports “Can’t resolve host name”

The name you specified for the remote host doesn’t correspond to an IP address. Depending on your network configuration, you may have a problem with your DNS server or your local “hosts” file.

•	TFTP Client95 consistently reports a block size of 512, regardless of what size I choose.

Specifying a block size causes TFTP Client95 to try to communicate with the TFTP server using the new Option Extension RFCs. If your server doesn’t support these options it will respond with a “standard” TFTP packet, causing TFTP Client95 to continue the transfer using the older standard.

•	TFTP Client95 reports:

Startup error: Ensure TCP/IP is properly installed

The IP protocol must be installed in order to use TFTP Client95.

Error: local file xxx already exists

If you want to overwrite a local file you must place a check mark in the “Overwrite if file exists” box.